Deterministic Reconfiguration of Measurement Modules Using Double Buffered DMA

ABSTRACT

Configuring at least one radio frequency (RF) instrument according to a plurality of RF measurement configurations for performing a plurality of tests on a device under test (DUT). A list of RF measurement configurations may be stored in a computer memory. The list of RF measurement configurations comprises a plurality of parameters for configuring operation of the at least one instrument. Information regarding the list of RF measurement configurations (e.g., a data stream) may be provided to the at least one RF instrument. The at least one RF instrument may perform the plurality of tests on the DUT, including the at least one RF instrument configuring itself according to the RF measurement configurations based on processing of the information. Configuring enables the at least one RF instrument to perform the plurality of tests on the DUT in a deterministic manner.

PRIORITY INFORMATION

This application claims benefit of priority of U.S. provisionalapplication Ser. No. 61/262,380 titled “Deterministic Reconfiguration ofMeasurement Modules” filed Nov. 18, 2009, whose inventors were SeadSuskic, Vince Shouba, Kunal Patel, and David Klipec which is herebyincorporated by reference in its entirety as though fully and completelyset forth herein.

FIELD OF THE INVENTION

The present invention relates to the field of measurement, and moreparticularly to a system and method for deterministic reconfiguration ofmeasurement modules.

DESCRIPTION OF THE RELATED ART

Measurement systems often include a host device that is in communicationwith other devices (measurement devices) to perform a desired task, suchas testing of a device under test. While performing such a task, it maybe desirable to change configurations of the measurement devices. Forexample, it may be desirable to perform a first test using themeasurement devices and then at a later time perform a second test usingthe measurement devices. However, in this example, it may be beneficialfor the reconfigurations to be performed automatically to provideflexibility and efficiency. Accordingly, improvements in device testingare desired.

SUMMARY OF THE INVENTION

Various embodiments are disclosed of a system and method for configuringat least one device according to a plurality of measurementconfigurations for performing a plurality of tests on a device undertest (DUT) (e.g., an RF DUT).

The device may receive a first one or more measurement configurations(e.g., RF measurement configurations) from a list of measurementconfigurations over a first DMA channel (e.g., from a host, such as acomputer system). The device may store the first one or more measurementconfigurations in a memory medium, e.g., a first buffer.

Accordingly, the device may configure itself according to a firstmeasurement configuration of the first one or more measurementconfigurations. Subsequent to configuring itself, the device may performat least a portion of one of the plurality of tests according to thefirst measurement configuration.

Prior to completion of the first one or more configurations (e.g.,completing corresponding tests using the first one or moreconfigurations), the device may request one or more second measurementconfigurations using the first DMA channel. Accordingly, the device mayreceive and store the second measurement configurations over the firstDMA channel, e.g., in a second buffer. Similar to above, the receivingand storing may be performed prior to completion of the first one ormore measurement configurations and the second measurementconfigurations may be available for configuring the at least one deviceupon completion of the first one or more measurement configurations.

Upon completion of the first one or more measurement configurations, thedevice may request one or more additional (third) measurementconfigurations, and, in response, the device may receive and store theone or more additional measurement configurations, e.g., in the firstbuffer.

Additionally, the device may configure itself to the secondconfigurations upon completion of the first configurations. In someembodiments, the device may initiate or cause the configuration bysending data over the first DMA channel. For example, the data may be“dummy” data, which does not serve a purpose other than initiating theconfiguration. However, in alternate embodiments, the data may serveanother purpose as well. Note that in some embodiments, the measurementconfigurations received by the device may also include addressinformation which may be used for sending the data.

Thus, in one embodiment, the device may perform the above configuring,requesting, receiving, and storing a plurality of times to perform theplurality of tests on the DUT in a deterministic manner.

BRIEF DESCRIPTION OF THE DRAWINGS

A better understanding of the present invention can be obtained when thefollowing detailed description of the preferred embodiment is consideredin conjunction with the following drawings, in which:

FIG. 1A illustrates a chassis system including a host device and atleast two other devices, which may be configured to implement variousembodiments of the present invention;

FIGS. 1B and 1C are exemplary block diagrams of the chassis system ofFIG. 1A;

FIGS. 2A-2C illustrates various exemplary systems which may beconfigured to implement various embodiments of the present invention;

FIG. 3 is a flowchart diagram illustrating one embodiment of a methodfor deterministic reconfiguration of measurement modules;

FIG. 4 illustrates an embodiment of a method for deterministicreconfiguration of measurement modules;

FIGS. 5A-5C are timing diagrams that illustrate timing of devicereconfiguration according to the method of FIG. 3;

FIGS. 6 and 7 are flowchart diagrams illustrating embodiments of amethod for deterministic reconfiguration of measurement modules usingdouble buffering;

FIG. 8 illustrates operation of the system according to the method ofFIG. 6;

FIGS. 9 and 10 are flowchart diagrams illustrating embodiments of amethod for open loop synchronization; and

FIG. 11 is an exemplary timing diagram corresponding to one embodimentof the method of FIG. 9.

While the invention is susceptible to various modifications andalternative forms, specific embodiments thereof are shown by way ofexample in the drawings and are herein described in detail. It should beunderstood, however, that the drawings and detailed description theretoare not intended to limit the invention to the particular formdisclosed, but on the contrary, the intention is to cover allmodifications, equivalents and alternatives falling within the spiritand scope of the present invention as defined by the appended claims.

DETAILED DESCRIPTION OF THE INVENTION Incorporation by Reference

The following references are hereby incorporated by reference in theirentirety as though fully and completely set forth herein:

U.S. Pat. No. 4,914,568 titled “Graphical System for Modeling a Processand Associated Method,” issued on Apr. 3, 1990.

U.S. Pat. No. 5,481,741 titled “Method and Apparatus for ProvidingAttribute Nodes in a Graphical Data Flow Environment”, issued on Jan. 2,1996.

U.S. Pat. No. 6,173,438 titled “Embedded Graphical Programming System”filed Aug. 18, 1997.

U.S. Pat. No. 6,219,628 titled “System and Method for Configuring anInstrument to Perform Measurement Functions Utilizing Conversion ofGraphical Programs into Hardware Implementations,” filed Aug. 18, 1997.

U.S. Patent Application Publication No. 20010020291 (Ser. No.09/745,023) titled “System and Method for Programmatically Generating aGraphical Program in Response to Program Information,” filed Dec. 20,2000.

U.S. Patent Application Publication 2008/0240321 (Ser. No. 11/695,139)titled “Aligning Timebases to Share Synchronized Periodic Signals,”filed Apr. 2, 2007.

U.S. Pat. No. 7,315,791, titled “Application programming interface forsynchronizing multiple instrumentation devices,” filed Feb. 18, 2004.

Terms

The following is a glossary of terms used in the present application:

Memory Medium—Any of various types of memory devices or storage devices.The term “memory medium” is intended to include an installation medium,e.g., a CD-ROM, floppy disks, or tape device; a computer system memoryor random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, RambusRAM, etc.; or a non-volatile memory such as a magnetic media, e.g., ahard drive, or optical storage. The memory medium may comprise othertypes of memory as well, or combinations thereof. In addition, thememory medium may be located in a first computer in which the programsare executed, and/or may be located in a second different computer whichconnects to the first computer over a network, such as the Internet. Inthe latter instance, the second computer may provide programinstructions to the first computer for execution. The term “memorymedium” may include two or more memory mediums which may reside indifferent locations, e.g., in different computers that are connectedover a network.

Carrier Medium—a memory medium as described above, as well as a physicaltransmission medium, such as a bus, network, and/or other physicaltransmission medium that conveys signals such as electrical,electromagnetic, or digital signals.

Programmable Hardware Element—includes various hardware devicescomprising multiple programmable function blocks connected via aprogrammable interconnect. Examples include FPGAs (Field ProgrammableGate Arrays), PLDs (Programmable Logic Devices), FPOAs (FieldProgrammable Object Arrays), and CPLDs (Complex PLDs). The programmablefunction blocks may range from fine grained (combinatorial logic or lookup tables) to coarse grained (arithmetic logic units or processorcores). A programmable hardware element may also be referred to as“reconfigurable logic”.

Program—the term “program” is intended to have the full breadth of itsordinary meaning The term “program” includes 1) a software program whichmay be stored in a memory and is executable by one or more processors or2) a hardware configuration program useable for configuring aprogrammable hardware element.

Software Program—the term “software program” is intended to have thefull breadth of its ordinary meaning, and includes any type of programinstructions, code, script and/or data, or combinations thereof, thatmay be stored in a memory medium and executed by one or more processors.Exemplary software programs include programs written in text-basedprogramming languages, such as C, C++, PASCAL, FORTRAN, COBOL, JAVA,assembly language, etc.; graphical programs (programs written ingraphical programming languages); programs that have been compiled tomachine language; scripts; and other types of executable software. Asoftware program may comprise two or more software programs thatinteroperate in some manner. Note that various embodiments describedherein may be implemented by a computer or software program. A softwareprogram may be stored as program instructions on a memory medium.

Hardware Configuration Program—a program, e.g., a netlist or bit file,that can be used to program or configure a programmable hardwareelement.

Computer System—any of various types of computing or processing systems,including a personal computer system (PC), mainframe computer system,workstation, network appliance, Internet appliance, personal digitalassistant (PDA), television system, grid computing system, or otherdevice or combinations of devices. In general, the term “computersystem” can be broadly defined to encompass any device (or combinationof devices) having at least one processor that executes instructionsfrom a memory medium.

Measurement Device—includes instruments, data acquisition devices, smartsensors, and any of various types of devices that are configured toacquire and/or store data. A measurement device may also optionally befurther configured to analyze or process the acquired or stored data.Examples of a measurement device include an instrument, such as atraditional stand-alone “box” instrument, a computer-based instrument(instrument on a card) or external instrument, a data acquisition card,a device external to a computer that operates similarly to a dataacquisition card, a smart sensor, one or more DAQ or measurement cardsor modules in a chassis, an image acquisition device, such as an imageacquisition (or machine vision) card (also called a video capture board)or smart camera, a motion control device, a robot having machine vision,and other similar types of devices. Exemplary “stand-alone” instrumentsinclude oscilloscopes, multimeters, signal analyzers, arbitrary waveformgenerators, spectroscopes, and similar measurement, test, or automationinstruments.

A measurement device may be further configured to perform controlfunctions, e.g., in response to analysis of the acquired or stored data.For example, the measurement device may send a control signal to anexternal system, such as a motion control system or to a sensor, inresponse to particular data. A measurement device may also be configuredto perform automation functions, i.e., may receive and analyze data, andissue automation control signals in response.

FIGS. 1A-1C—Chassis 50

FIGS. 1A-1C illustrate an exemplary chassis 50. As shown in FIGS. 1A and1B, the chassis 50 may include a host device 100 (e.g., a hostcontroller board), which may include a CPU 105, memory 110, and chipset115. Other functions that may be found on the host device 100 arerepresented by the miscellaneous functions block 120. In someembodiments, the host device may include a processor and memory (asshown) and/or may include a programmable hardware element (e.g., a fieldprogrammable gate array (FPGA)). In embodiments where the host deviceincludes a programmable hardware element, it may be configured accordingto a graphical program as described in the various patents incorporatedby reference above.

As shown, the host device 100 (e.g., the chipset 115 of the host device100) may provide communication (e.g., PCIe communication, PXIcommunication, or other bus communication) to a first peripheral device125 and a second peripheral device 150 over bus 175. The firstperipheral device 125 and second peripheral device 150 may be configuredto change configurations based on information provided by the hostdevice 100, as described herein.

The devices may be any of various devices (e.g., PCIe devices), such asmeasurement devices (e.g., DAQ devices), processing devices, I/Odevices, network devices, etc. Additionally, similar to above, thedevices may include one or more programmable hardware elements orprocessors and memory to implement their respective functionality. Insome embodiments, the 125 and the device 150 may include a DMAcontroller (130 and 155 respectively) to perform DMA transfers, e.g., toperform the transfers of data described herein.

As indicated above, embodiments of chassis 50 may be used in test andmeasurement systems, such as systems used to acquire, process or outputdata relating to a device or process being monitored or controlled, forinstance. Accordingly, such a system may acquire data, and subsequentlytransfer the data for processing, storage, output, or the like. Forexample, in the case of chassis 50 being used to control a process(e.g., a closed loop system) data may be acquired, transferred to aprocessor where it may be processed, and subsequently transferred to anoutput such that the processed output may be employed to appropriatelycontrol the respective process.

FIG. 1C illustrates an exemplary embodiment of a system, e.g., a modularPXI-based RF test system, which may implement various embodiments of themethods described herein. More specifically, as shown, the chassis 50may be a PXI express chassis which may include an embedded chassiscontroller 100. Within the chassis 50, the chassis controller 100 may becoupled to a vector signal generator (VSG) 125 and a vector signalanalyzer (VSA) 150, e.g., over a PXI express bus. As shown, the VSG 125may include a local oscillator (LO) 126, an up converter 127, and anarbitrary waveform generator (AWG) 128. Similarly, the VSA may includeLO 151, down converter 152, and digitizer 153.

The VSG and VSA may both be coupled to a device under test (DUT) or unitunder test (UUT) 180, e.g., via an RF connection, depending on theembodiment. More particularly, in one embodiment, the VSG 125 may coupleto one port of DUT 180 to provide a stimulus signal. The VSA 150 maycouple to a different port on the DUT to acquire and measure the DUT'sresponse to the stimulus. Note that FIG. 1C provides a generalrepresentation of a modular test system, and while this diagram presentsa system with a VSA, a VSG, and a DUT, in practice, these systems mighthave only a VSA or VSG, and a DUT. For example, the system may be usedto characterize the DUT's transmitter, or the DUT's receiver, or both,although other devices and configurations are envisioned.

In some embodiments, the VSG 125 and VSA 150 may correctly interfacewith the DUT as long as the accompanying driver software is used toapply the appropriate RF configuration to the two devices. Consequently,if the devices' RF configuration needs to be changed because the DUT RFsettings change, the controlling program may call the appropriatefunctions in the VSA and VSG driver software. However, certain DUTs havesuch requirements that the RF configuration changes are not acceptablein terms of timing repeatability. In these particular cases, the methodsdescribed herein may be used to make the configuration changes (e.g.,the RF configuration changes) deterministic.

Thus, FIG. 1C illustrates a particular embodiment where the devices 125and 150 are used to test a DUT (e.g., an RF DUT). More specificembodiments which may be applicable to FIGS. 1A-1C (and in particular,1C) are provided below.

FIGS. 2A-2C—Exemplary Measurement Systems

FIGS. 2A-2C illustrate host device 100 as a computer system. As shown inFIG. 2A, the host device 100 may be coupled to chassis 50 (e.g.,including the first device 125 and the second device 150) and mayinclude a display device and one or more input devices. Similar todescriptions of the host device 100 above, the host may include at leastone memory medium on which one or more computer programs or softwarecomponents according to one embodiment of the present invention may bestored. The memory medium may also store operating system software, aswell as other software for operation of the computer system. Variousembodiments further include receiving or storing instructions and/ordata implemented in accordance with the foregoing description upon acarrier medium.

In various embodiments, the host device 100 may be coupled to a secondcomputer system or device via a network (or a computer bus). Thecomputer systems may each be any of various types, as desired. Thenetwork can also be any of various types, including a LAN (local areanetwork), WAN (wide area network), the Internet, or an Intranet, amongothers.

FIG. 2B illustrates an exemplary instrumentation control system whichmay implement embodiments of the invention. As shown, the systemcomprises a host device 100 which couples to one or more other devices(e.g., which may be the device 125 and/or the device 150 describedabove). The host device may operate with the one or more devices toanalyze, measure or control a unit under test (DUT) or process.

The one or more devices may include a GPIB instrument 212 and associatedGPIB interface card 222, a data acquisition board 214 inserted into orotherwise coupled with chassis 224 with associated signal conditioningcircuitry 226, a VXI instrument 216, a PXI instrument 218, a videodevice or camera 232 and associated image acquisition (or machinevision) card 234, a motion control device 236 and associated motioncontrol interface card 238, and/or one or more computer based instrumentcards 242, among other types of devices. The computer system may coupleto and operate with one or more of these devices. The instruments may becoupled to the unit under test (UUT) or process, or may be coupled toreceive field signals, typically generated by transducers. The systemmay be used in a data acquisition and control application, in a test andmeasurement application, an image processing or machine visionapplication, a process control application, a man-machine interfaceapplication, a simulation application, or a hardware-in-the-loopvalidation application, among others.

FIG. 2C illustrates an exemplary industrial automation system which mayimplement embodiments of the invention. The industrial automation systemis similar to the instrumentation or test and measurement system shownin FIG. 2B. Elements which are similar or identical to elements in FIG.2B have the same reference numerals for convenience. The system maycomprise a host device 100 which couples to one or more devices orinstruments. Similar to above, the host device 100 may comprise a CPU, adisplay screen, memory, and one or more input devices such as a mouse orkeyboard as shown. The host device 100 may operate with the one or moredevices to perform an automation function with respect to a process ordevice, such as MMI (Man Machine Interface), SCADA (Supervisory Controland Data Acquisition), portable or distributed data acquisition, processcontrol, advanced analysis, or other control, among others.

The one or more devices may include a data acquisition board 214inserted into or otherwise coupled with chassis 224 with associatedsignal conditioning circuitry 226, a PXI instrument 218, a video device232 and associated image acquisition card 234, a motion control device236 and associated motion control interface card 238, a fieldbus device270 and associated fieldbus interface card 272, a PLC (ProgrammableLogic Controller) 276, a serial instrument 182 and associated serialinterface card 284, or a distributed data acquisition system, such asthe Fieldpoint system available from National Instruments, among othertypes of devices.

FIG. 3—Configuration Changes for One or More Devices

FIG. 3 illustrates a method for changing configurations for one or moredevices. The method shown in FIG. 3 may be used in conjunction with anyof the computer systems or devices shown in the above Figures, amongother devices. In various embodiments, some of the method elements shownmay be performed concurrently, in a different order than shown, or maybe omitted. Additional method elements may also be performed as desired.As shown, this method may operate as follows.

In 302, a list of configurations may be created, e.g., by a user orprogram. For example, in one embodiment, the user may create a list ofRF configurations for testing an RF device. However, while the methoddescribed herein is applied to RF devices, it may be applied to any typeof device or system, as desired. The list of RF configurations mayinclude a set of RF instrument options, e.g., for each listedconfiguration, which may be set via the application programminginterface (API) of an RF instrument driver.

The list of RF configurations may also include a specification of how tomove the instrument from one item in the RF configuration set toanother. For example, the API may allow the user to directly configurethe use of a trigger bus, e.g., a PXI trigger bus for the purposes ofadvancing the RF devices through the RF list, e.g., specifying aconfiguration list step trigger source.

In one embodiment, the list of configurations may be specified using ahost computer, such as the host 100 described above, although otherdevices are envisioned. The list of configurations may be specifiedgraphically, e.g., in a graphical program, or textually as desired.Graphical program 410 of FIG. 4 illustrates a graphical program whichspecifies the configuration list using a graphical API.

In 304, from the list of RF configurations (e.g., specified using theAPI), an intermediate representation of the list may be created, e.g.,by an instrument driver. The intermediate representation may be createdby the host device. Additionally, the internal RF list representationmay include synchronization instructions for each module that mayeffectively allow the configuration changes on each device to happen atapproximately the same time (e.g., within a few micro or milliseconds).For this purpose, a device driver may be used to automatically programthe modules to use a common bus, e.g., a PXI trigger bus. As indicatedabove, the assignment of the trigger bus may be provided using the APIspecification, e.g., by a user.

In 306, data streams may be created for each device involved in thetest, e.g., each of the modules of the PXI-based RF instrument. FIG. 4,described below, illustrates this process for a VSG instrument, althoughthis may similarly apply to a VSA instrument.

In 308, the devices (or modules of the devices) may be configuredaccording to the data streams, e.g., while testing the DUT. Thus,according to the method of FIG. 3, a DUT may be tested by configuringone or more devices according to the list of configurations in adeterministic manner. Further descriptions of the mechanism for changingconfigurations and triggering the change of configurations are providedbelow.

FIGS. 4-5C—Exemplary Diagrams Corresponding to FIG. 3

FIG. 4 is an exemplary diagram illustrating the method of FIG. 3 appliedto three modules of a device (e.g., a VSG device). As indicated above,similar depictions and descriptions apply to other devices, such as aVSA device.

As shown in FIG. 4, the list of configurations may be specifiedgraphically, e.g., in graphical program 410. More specifically, thegraphical program 410 illustrates a graphical program which specifiesthe configuration list using a graphical API.

From the graphical specification of the configuration list, an internalrepresentation of the configuration list is created, shown as 420.

As shown in FIG. 4, each module of the device includes a list processingunit (LPU) that is configured to accept an appropriately formed list,e.g., the data stream for that module, in a real-time and deterministicmanner. Each of these module-specific, low-level lists has theinstructions on how to program the corresponding RF configuration oneach module.

However, the generated data stream for each module may cause programmingof each module in a specific order. For example, in the case of the VSG,FIG. 5A represents an exemplary sequence (in a timing diagram 500) ofhardware programming as executed by the appropriate LPU for one step. Inthis case, the config trig (the configuration trigger) may be receivedby all three modules, and the diagram illustrates the programmingsequence for each module.

More particularly, as shown in FIG. 5A, the up converter module, the AWGmodule, and the LO module may each wait for the configuration triggeruntil it is received as shown. Accordingly, the up converter may firstwrite registers and decrement power, then wait N μSec (where N allowsthe LO module to finish writing frequency registers), and then incrementpower (write registers). The AWG module, after receiving theconfiguration trigger, may also wait M μSec (where M allows the LOmodule to finish writing frequency registers) and then changeconfiguration if the digital gain is being increased. Finally, the LOmodule, upon receiving the configuration trigger, may wait J μSec toallow the up converter to decrease power, decrease its own power (writeregisters), change frequency (write registers), and increase power(write registers). Once the LO completes these steps, the up converterand AWG modules may increment power and change configuration ifincreasing digital gain, respectively.

FIG. 5B illustrates the programming sequence when the AWG module changesconfiguration for decreasing digital gain before waiting M time and whenthe AWG module has to wait additional time for completion of upconverter I/O, e.g., time required for up converter transactions. FIG.5C illustrates the programming sequence when the AWG has to waitadditional time for required LO transactions.

Note that the values of M, N, and J above may be 0 or greater, dependingon the processes being performed by the various other modules ordevices.

FIG. 6—Double Buffering Measurement Configurations

The following section specifically relates to an additional embodimentfor configuring devices while testing a DUT. More specifically, doublebuffered measurement configurations may be used to modify theconfiguration list while testing is performed on the DUT. Thus, themethod of FIG. 3 may be modified to include the following embodiments.In various embodiments, some of the method elements shown may beperformed concurrently, in a different order than shown, or may beomitted. Additional method elements may also be performed as desired. Asshown, this method may operate as follows.

In 602, the device may receive a first one or more (e.g., a pluralityof) measurement configurations (e.g., RF measurement configurations)from a list of measurement configurations over a first DMA channel(e.g., from a host, such as a computer system). For example, the devicemay receive the measurement configurations from a host coupled to thedevice, e.g., from within a chassis, or external to a chassis, asdesired.

The measurement configurations may be created and conveyed as describedabove, e.g., with respect to FIG. 3. For example, in one embodiment, themeasurement configurations may be received as a data stream over a DMAchannel. In some embodiments, the measurement configurations may bereceived as instructions embedded in DMA links. The device may store thefirst one or more measurement configurations in a memory medium, e.g., afirst buffer. According to various embodiments, the first one or moremeasurement configurations may be a single configuration, or, morecommonly, a plurality of measurement configurations. In someembodiments, the buffer may be a 2 k buffer which may store 100configurations, although the buffer may be of various sizes for storingvarious numbers of configurations (e.g., 2, 5, 10, 20, 50, 100, 200, 500configurations). A full capacity link of configurations may be referredto as a “chunky” link.

Accordingly, in 604, the device may configure itself according to afirst measurement configuration of the first one or more measurementconfigurations. Each measurement configuration may be specified by oneor more configuration links (e.g., where DMA links are used forconfiguration). The device may know how many of the configuration linksto execute by looking for a marker between configurations (e.g., a pagedescription between configuration links).

Subsequent to configuring itself, the device may begin performing one ofthe plurality of tests according to the first measurement configuration.For example, the first configuration may be used by the device toinitiate a first test of the plurality of tests. In some embodiments,each configuration may be associated with a particular test, or aplurality of configurations may be required for a test, among variousoptions.

In some embodiments, the device may initiate or cause the configurationby sending data over the first DMA channel. For example, the data may be“dummy” data, which does not serve a purpose other than initiating theconfiguration. Thus, by sending the data, the device may cause itself toexecute the DMA links stored in the first buffer. However, in alternateembodiments, the data may serve another purpose as well. Note that insome embodiments, the measurement configurations received by the devicemay also include address information which may be used for sending thedata.

Prior to completion of the first one or more configurations (e.g.,completing corresponding tests using the first one or moreconfigurations), in 606, the device may request one or more secondmeasurement configurations using the first DMA channel. Accordingly, thedevice may receive and store the second measurement configurations overthe first DMA channel, e.g., in a second buffer. Similar to above, thereceiving and storing may be performed prior to completion of the firstone or more measurement configurations and the second measurementconfigurations may be available for configuring the at least one deviceupon completion of the first one or more measurement configurations. Asused herein, “completion of measurement configurations” refers to thedevice performing whatever test (or portion of a test) for which themeasurement configuration is associated. Thus, where a VSG needs togenerate a specific signal using a specific configuration, upongenerating the signal according to the configuration, the configurationmay be “completed” and the device may configure itself according to thenext configuration. Thus, once the device has performed whatever actionor test is associated with a configuration and a next test needs to beperformed, the device has “completed” that measurement configuration. Insome embodiments, the device may be notified that it has “completed” aconfiguration upon reception of a trigger (e.g., for triggering aplurality of devices) or upon reaching a predetermined time foradvancing to the next configuration.

In one embodiment, the second one or more configurations may be receivedin response to the sending of the data over the DMA channel describedabove, e.g., when of the buffers or available (e.g., in this case, wherethe second buffer is empty). Thus, whenever new configurations areexecuted and there is room in a buffer available (e.g., when the bufferis completely unused), new configurations may be stored in the availablebuffer. Note that in this embodiment, where there are a plurality ofreceived configurations, the reception of additional configurations maynot occur each time data is sent over the DMA channel. Instead,additional configurations may not be requested or received unless thereis space available in a buffer. However, where only a singleconfiguration is stored in each buffer, the additional configurationsmay be received each time a configuration is used, thereby ensuring thata new configuration is always available upon completion of the previousconfiguration, without having to wait to receive the new configuration.In alternate embodiments, new configurations may be stored wheneverspace is available in a buffer, regardless of whether the buffer iscompletely available or only partially available.

Upon completion of the first one or more measurement configurations, in608, the device may request one or more additional (third) measurementconfigurations, and, in response, the device may receive and store theone or more additional measurement configurations, e.g., in the firstbuffer. More specifically, in embodiments where the first one or moremeasurement configurations initially take up the entirety of the firstbuffer, once those are “completed”, third measurement configurations maybe requested. Similar to above, the configurations may be received in adata stream over the DMA channel. Additionally, the device may configureitself to the second configurations (e.g., a first configuration of thesecond configurations) upon completion of the first configurations.Similar to above, this process may be invoked by sending data to thehost over the DMA channel, as desired.

Thus, in one embodiment, the device may perform the above configuring,requesting, receiving, and storing a plurality of times to perform theplurality of tests on the DUT in a deterministic manner. Note that usingembodiments described herein, the device may be configured according toan arbitrary number of configurations which may be changed “on the fly”since they are being provided in the manner described. For example, auser may change the order of configurations or the number of futureconfigurations at any time during testing of the DUT, assuming thoseconfigurations have not already been fetched and/or “completed” by thedevice(s).

FIGS. 7 and 8—Specific Embodiments of Double Buffering

FIGS. 7 and 8 provide a more specific embodiment of the double bufferingof measurement configurations described in FIG. 6. The method shown inFIG. 7 may be used in conjunction with any of the computer systems ordevices shown in the above Figures, among other devices. In variousembodiments, some of the method elements shown may be performedconcurrently, in a different order than shown, or may be omitted.Additional method elements may also be performed as desired. FIG. 8shows a representation of the over-all system diagram, specifically forthe base-band digitizer. Note that this section may particularly applyto digitizers and arbitrary waveform generators, also known as base-bandmodules in modular (e.g., PXI-based) RF instruments. However, thedetails relating to the double-buffered DMA apply equally to otherdevices, such as AWGs.

In 702, the timing engine in the hardware (section 810 of FIG. 8), mayinterrupt the microprocessor (e.g., the LPU 862, which may be an 8051microprocessor) (section 820). Note that 820 of FIG. 8 may be referredto as the “chinch” portion, which may be hardware (e.g., an ASIC) whichabstracts a hardware device from the bus (e.g., PXI, PXIe, PCI), e.g.,for PXIe. According to some embodiments, this may be performed in aperiodic fashion, e.g., at regular hardware-timed intervals. In someembodiments, this may occur at an “end of record” of acquired data onthe baseband digitizer.

In 704, the microprocessor 862 may write a piece of data into thestreaming FIFO 864 causing, in 706, the DMA engine 870 to execute theDMA links, e.g., instructions.

During the process, in 708, the DMA engine may automatically pre-fetchthe next DMA link from the host system (buffer 874) to the device(device registers 866). This DMA transfer may include low levelinstructions corresponding to the list of configurations. Accordingly,while the DUT is being tested, the device may receive and be configuredaccording to the list of configurations. The device (e.g., the chinch820) may configure itself using link processor 868. Note that linkprocessor 868 may normally (e.g., for typical DMA operations) load theaddress on the host to send and receive data from. However, as describedherein, the link processor 868 may cause or perform configuration of thedevice by processing configuration links, e.g., in response to sendingdata to the host, such as dummy data. Additionally, because theconfigurations are provided during the testing of the DUT in thisembodiment, the list of configurations may be changed “on the fly”,allowing the list of configurations to be reordered, added to, etc.while the DUT is being tested.

The following provides one specific example describing how the number ofconfiguration links to execute is determined. However, this is exemplaryonly and other methods are envisioned.

In a normal DMA operation, the configuration links may include theaddress on the host to send data to and the contiguous amount of addressspace available from that address. In this example, 100 bytes may besent from the device to the host. Accordingly, on the host, only two 50byte segments of contiguous RAM may be available. Based on this, thehost may send two configuration links with starting address of thesegments of RAM on the host and the number of bytes in those segments(in this example 50) to the DMA channel on the device. If the devicesends 50 bytes to the DMA channel, it will execute the firstconfiguration link and wait for more data from the device beforeexecuting the next configuration link.

This “pausing ability” of the DMA channel may be used to throttle theexecution of the configuration links. In this example, a configurationlink that has a host RAM address may be referred to as a “pagedescriptor” link and a configuration link that has the specialinstruction to write a register may be referred to as a “self config”link. Accordingly, an instruction list with two steps and two writeregister commands could appear as:

1. Page descriptor, 2. Self config link, 3. Self config link, 4. Pagedescriptor, 5. Self config link, 6. Self config link

Each time the hardware pushes a piece of data (e.g., dummy data) intothe DMA channel, one of the page descriptors and all of the self configlinks behind it may be executed until the DMA channel hits another pagedescriptor. At this point the DMA channel may pause (because thehardware hasn't pushed any additional data into the DMA channel, atleast until the next step).

As shown in FIG. 8, the channel data 852 from the device may be providedfrom on board memory 854 to DMA channel 856 to the host (user buffer858). The host may also provide information back to the DMA channel 856via buffer 860. In one embodiment, the device driver may be used tocreate data structures stored in buffers 860 and 874. Buffer 874 maystore a data structure which includes hardware configurationinstructions in addition to DMA related content. Note that in the caseof an AWG, the data may be provided in the reverse direction, from thehost to the device. Thus, using the DMA channel 856, data istransferred, and using the DMA channel 870, the device may be configuredaccording to the list of configurations. Thus, by using two separate DMAchannels, the process may be deterministic and unaffected by other hostand bus traffic.

FIGS. 9 and 10—Open Loop Synchronization Using Self-Correcting Timers

In test and measurement, various different modules or subsystems runningat different clock, sample, or update rates may need to be synchronized.As used herein, synchronization is the process of ensuring signals oneach module or subsystem can occur either simultaneously, or atprecisely controlled times with respect to one other.

As described above, a list of configurations may be used to sequence oneor more test and measurement devices (“devices”) through a series ofreconfigurations. Each reconfiguration may change one or morecharacteristics of the test and measurement devices, includingfrequency, power level, and other parameters. As also described, thelist of configurations may be used to synchronize the reconfigurationtimes of one or more devices with each other and, if desired, a DUT. Forexample, consider the following sequence:

Two VSGs generate a stimulus waveform.

A DUT responds to the stimulus.

A VSA measures the DUT's response waveform.

Every 100 ms, the two VSGs simultaneously reconfigure to a newfrequency.

Every 200 ms, but aligned 5 ms before a stimulus change, the VSAreconfigures to a new power level.

FIG. 9 illustrates a method for open loop synchronization usingself-correcting timers, which may be applicable to the above scenario.The self-correcting timer mechanism, described below, may be implementedon any of the devices or modules described herein. For example, it maybe implemented on any device that regulates reconfigurations, e.g.,modules that drive a configuration trigger. Thus, the method shown inFIG. 9 may be used in conjunction with any of the computer systems ordevices shown in the above Figures, among other devices. For example,the method of FIG. 9 may be used to keep multiple devices in synchacross multiple iterations and/or configuration changes. In variousembodiments, some of the method elements shown may be performedconcurrently, in a different order than shown, or may be omitted.Additional method elements may also be performed as desired. As shown,this method may operate as follows.

In 902, each device may establish a timer, e.g., implemented as aclocked counter, that can be selected as the source for theconfiguration trigger. In one embodiment, to avoid cumulative timingdrift over the course of an operation, especially a long or continuousoperation, a common time reference that is shared between all thedevices may be established. Note that the common time reference may alsoapply to the DUT.

In general, the devices may be configured to share a frequencyreference, a trigger, or both. Each of the devices may (a) use thefrequency reference directly as a clock or (b) derive one or more clocksfrom the frequency reference. Circuits such as phase-locked loops,digital locked loops, and clock dividers may be used to derive clockslocked to the frequency reference. If starting alignment is important,the devices may also share a trigger to establish a common “time zero”.See U.S. Publication 2008/0240321 and U.S. Pat. No. 7,315,791,incorporated by reference above, for further details on techniques thatcan improve determinism when sharing triggers. Thus, where a commonfrequency reference is used, the counter's clock may be the frequencyreference or some clock locked to the frequency reference. Additionallyor alternatively, if a common trigger is used, depending on the type oftrigger, the counter may be started by the trigger or the position ofthe trigger may be recorded relative to the counter. In one embodiment,the timer may be implemented as an incrementing counter that starts fromzero.

Once the timer begins counting, in 904, it may continue without pauseor, if it pauses, may pause only for a known and deterministic time. Forexample, where the timer is implemented as a counter, it may tally everyclock edge without pause. By never pausing (or pausing only for knowntimes), the timer may obviate any need to synchronize pauses with otherdevices. The timer may continue for the duration of the list ofconfigurations or testing of the DUT.

In one embodiment, the counter may be programmed initially with thefirst desired interval for generating a configuration trigger: Eachinterval may be rounded (for example, truncated) to an integer number ofclock cycles. At the expiration of the interval, the timer may emit aconfiguration trigger. In one embodiment, the interval is aterminal-count register for the incrementing counter. The timer may“roll over” and reset to its initial count after reaching the terminalcount. However, the reset process may not pause the timer (unless for aknown time), e.g., the timer may continue to advance deterministically.Subsequently, the timer may be loaded with the value for each successiveinterval, if different. As with resetting, the process of loading a newinterval value may not pause the timer (unless for a known time); thetimer may continue to advance deterministically.

In 906, the device (e.g., each device) may track and eliminate(self-correct) any rounding error over time: Rounding to an integernumber of clock cycles typically introduces error. When the accumulatederror exceeds one clock cycle, a cycle may be added to or subtractedfrom the next timer interval to correct. For example, if the firstdesired interval is 150.5 clocks, the timer may be programmed for 150clocks. If the second desired interval is also 150.5 clocks, the timermay be programmed for 151 clocks: the new desired interval, plus acorrection for the accumulated error. The error tracking is equivalentto implementing additional, less-significant bits on the timer below theunits bit—that is, to implementing fractional bits. The desired timingprecision dictates the number of fractional bits required. Forsingle-iteration operation, it may be possible to pre-compute therounded timer values. However, to support a general case that mayinclude continuous or looping operation, the device may tally andcompensate for rounding error while running In one embodiment, thefractional bits may be implemented using an adder in an arithmetic logicunit under control of an embedded program. Alternatively, e.g., where anarithmetic logic unit is unavailable or undesirable, fractional-bittracking may be added to the timer hardware.

However, it should be noted that care should be taken in rounding: Theclock rate of the timer should be fast enough relative to thereconfiguration intervals that the jitter introduced by rounding to aninteger clock cycle is acceptable. In the case of continuous or loopingoperation, the same interval on different loop iterations may vary inlength by one clock cycle due to rounding. Optionally, thiscycle-to-cycle variation may be isolated to a single step of therecurring sequence. This can be accomplished by pre-computing therounded timer values for all steps except one, and the rounded timervalues for the remaining step may be computed while running.

In some embodiments, the clocks, update, and sample rates of the variousdevices in the system can differ. In this case, the rounding on eachdevice may be different. However, each device may be configured toself-correct to “absolute time”. Assuming that the devices share acommon frequency reference (or have sufficiently precise and stableindependent frequency references) and that sufficient precision is usedin the error-tracking math, the devices do not drift significantly fromeach other over time.

FIG. 10 illustrates an exemplary embodiment of the method for open loopsynchronization using self-correcting timers, which may be applicable tothe above scenario. Note that while the specific examples andembodiments of FIG. 9 may be applicable to the embodiment of FIG. 10,they do not limit the scope of following embodiments. FIG. 10 isdescribed in the context of a loop, which may loop over multipleiterations, each iteration including one or more steps. Each step may beassociated with a particular action (e.g., a configuration or test). Insome embodiments, each iteration may be the same as the next, e.g., eachiteration may include a plurality of configurations for testing a DUT,and those configurations may continue to execute in an “open” manneruntil they are stopped or changed. However, other embodiments areenvisioned where each iteration includes different steps, as desired.

Various embodiments are disclosed of a system and method for maintainingsynchronization among a plurality of devices using clocks, wherein theplurality of devices operate together for a plurality of iterations in alooped manner.

In 1002, each device may establish a clock based on a common signal orsignals. For example, as indicated above, the common signals may be afrequency reference and/or trigger, as desired. Each clock may not pauseand may have a constant relationship with each other clock over time.

In 1004, each device may round a first step time of a first step of afirst iteration to one of two first nearest clock cycles, e.g., wherethe first step time does not occur on either of the two first nearestclock cycles. In some embodiments, the rounding may be to the absolutenearest clock cycle (e.g., to the clock cycle immediately before orafter the first step time). Alternatively, the rounding may be performedto the nearest clock cycle before the first step time or the nearestclock cycle after the first step time, as desired.

In 1006, upon reaching the one of the two first nearest clock cycles,each device may perform a respective first action in a synchronizedmanner with respect to the other devices. In one embodiment, the actionmay be a reconfiguration, e.g., which determines device or testparameters, including the next step time. For example, the next steptime may be determined based on received information which specifies thereconfiguration. Alternatively, or additionally, each step time may bedetermined based on a counter (e.g., a non-pausing counter) for theclock. In some embodiments, each step time may be based as an incrementfrom the previous step, or a cumulative time, as desired.

In 1008, over one or more additional steps of the loop, each device mayadjust clock cycles for each of the one or more additional steps toremove rounding error. The adjustment may be performed dynamicallyduring run time. Upon reaching the end of a step, each device mayperform a respective action in a synchronized manner with respect to theother devices.

Thus, the method described above may be performed a plurality of timesover various steps. For example, the method may be performed each stepof each iteration, or possibly for one or more steps in each iteration(thus adjusting for rounding errors in each iteration). In oneembodiment, for example, each device may round a second step time of asecond step of the first iteration to one of two second nearest clockcycles and the second rounding may incorporate the rounding of the firststep time of the first step. Correspondingly, the determined clockcycle, each device may perform a respective second action in asynchronized manner with respect to the other devices.

FIG. 11—Exemplary Timing Diagram

FIG. 11 illustrates a timing diagram showing two devices performingtasks according to one embodiment of the synchronization describedabove. As shown, a first device (dev 1) may operate at a clock ratewhich is slower than the clock rate of a second device (dev 2). Thesetwo devices may perform tasks over multiple steps and iterations in asynchronized manner

As shown, at time 0, both devices may receive a trigger to use as acommon start or reference time. Each device may then determine (orreceive) a nearest clock cycle before the next step (a dotted line showsthe start of each step). In this instance, device 1 determines that thenext task should begin after three clocks for iteration 1, step 1, fourclocks for iteration 1, step 2, four clocks for iteration 2, step 1(which resolves all of the accumulated error from the previous twosteps), and three clocks for iteration 2, step 2. Similarly, device 2(operating with a faster clock, and therefore having less error on anygiven iteration) determines that the next task should begin after fiveclocks, six clocks, five clocks, and six clocks for each respectivestep. Thus, the two devices both use clocks to monitor error overmultiple steps and iterations and are able to perform the changes oftasks in a synchronized manner.

Applicability to Configuration Lists

When incorporated in the configuration lists described above, the timerintervals themselves can be modified as part of a reconfiguration.Therefore, the sequence of configuration trigger times is arbitrary andpotentially infinite. If desired, the sequence of intervals can differfor different devices. The self-correcting timer mechanism, whileparticularly applicable for the needs of lists of configurationsdescribed herein, may have more general application to synchronizationof events across devices for any of various purposes.

Advantages of Open-Loop Synchronization

Various embodiments of the open-loop synchronization, described above,offers several benefits:

Supports “open loop” operation: that is, it may not require signalexchange, other than (optionally) a frequency reference and a one-timetrigger to establish a common time reference.

Supports heterogeneous operation: The mechanism can synchronize similaror dissimilar devices running at similar or dissimilar clock, sample,and update rates.

Achieves high accuracy. Dissimilar devices need not drift over time, andabsolute time accuracy is limited only by the stability and precision ofthe frequency reference.

Supports both single-iteration and continuous, looping operation.

Requires no special circuitry on the DUT.

Although the embodiments above have been described in considerabledetail, numerous variations and modifications will become apparent tothose skilled in the art once the above disclosure is fully appreciated.It is intended that the following claims be interpreted to embrace allsuch variations and modifications.

1. A method for configuring at least one device according to a pluralityof measurement configurations for performing a plurality of tests on adevice under test (DUT), the method comprising: receiving, by the atleast one device, a first one or more measurement configurations from alist of measurement configurations over a first DMA channel; the atleast one device storing the first one or more measurementconfigurations; the at least one device configuring itself according toa first measurement configuration of the first one or more measurementconfigurations; the at least one device performing at least a portion ofone of the plurality of tests according to the first measurementconfiguration; the at least one device requesting one or more furthermeasurement configurations using the first DMA channel prior tocompletion of the first one or more measurement configurations;receiving and storing, by the at least one device, the one or morefurther measurement configurations over the first DMA channel inresponse to said requesting the one or more further measurementconfigurations, wherein said receiving and storing is performed prior tocompletion of the first one or more measurement configurations, whereinthe one or more further measurement configurations are available forconfiguring the at least one device upon completion of the first one ormore measurement configurations.
 2. The method of claim 1, wherein thefirst one or more measurement configurations are stored in a firstbuffer and the second one or more measurement configurations are storedin a second buffer.
 3. The method of claim 2, further comprising: uponcompletion of the first one or more measurement configurations, the atleast one device requesting one or more additional measurementconfigurations; and in response to the request for the one or moreadditional measurement configurations, the at least one device receivingand storing the one or more additional measurement configurations in thefirst buffer.
 4. The method of claim 1, further comprising: performingsaid configuring, said requesting, and said receiving and storing aplurality of times to perform the plurality of tests on the DUT in adeterministic manner.
 5. The method of claim 1, further comprising: theat least one device sending data over the first DMA channel to configureitself according to a first measurement configuration of the one or morefurther measurement configurations.
 6. The method of claim 5, whereinthe data comprises dummy data.
 7. The method of claim 5, wherein saidreceiving the one or more further measurement configurations comprisesreceiving address information and the one or more further measurementconfigurations over the DMA channel in response to the at least onedevice sending the data over the first DMA channel.
 8. The method ofclaim 1, wherein the DUT comprises a radio frequency (RF) DUT, andwherein the plurality of measurement configurations are RF measurementconfigurations.
 9. A device capable of being configured according to aplurality of measurement configurations for performing a plurality oftests on a device under test (DUT), wherein the device comprises: one ormore buffers; and logic coupled to the one or more buffers, wherein thelogic is configured to perform: receiving a first one or moremeasurement configurations from a list of measurement configurationsover a first DMA channel; storing the first one or more measurementconfigurations in the one or more buffers; configuring the deviceaccording to a first measurement configuration of the first one or moremeasurement configurations; performing at least a portion of one of theplurality of tests according to the first measurement configuration;requesting one or more further measurement configurations using thefirst DMA channel prior to completion of the first one or moremeasurement configurations; receiving and storing the one or morefurther measurement configurations over the first DMA channel in the oneor more buffers in response to said requesting the one or more furthermeasurement configurations, wherein said receiving and storing isperformed prior to completion of the first one or more measurementconfigurations, wherein the one or more further measurementconfigurations are available for configuring the device upon completionof the first one or more measurement configurations.
 10. The device ofclaim 9, wherein the one or more buffers comprise a first buffer and asecond buffer, and wherein the first one or more measurementconfigurations are stored in the first buffer and the second one or moremeasurement configurations are stored in the second buffer.
 11. Thedevice of claim 10, wherein the logic is further configured to perform:upon completion of the first one or more measurement configurations,requesting one or more additional measurement configurations; and inresponse to the request for the one or more additional measurementconfigurations, receiving and storing the one or more additionalmeasurement configurations in the first buffer.
 12. The device of claim9, wherein the logic is further configured to perform said configuring,said requesting, and said receiving and storing a plurality of times toperform the plurality of tests on the DUT in a deterministic manner. 13.The device of claim 9, wherein the logic is further configured toperform: sending data over the first DMA channel to configure itselfaccording to a first measurement configuration of the one or morefurther measurement configurations.
 14. The device of claim 13, whereinthe data comprises dummy data.
 15. The device of claim 13, wherein saidreceiving the one or more further measurement configurations comprisesreceiving address information and the one or more further measurementconfigurations over the DMA channel in response to said sending the dataover the first DMA channel.
 16. The device of claim 9, wherein the DUTcomprises a radio frequency (RF) DUT, and wherein the plurality ofmeasurement configurations are RF measurement configurations.
 17. Acomputer accessible memory medium storing program instructions forconfiguring at least one device according to a plurality of measurementconfigurations in order to perform a plurality of tests on a deviceunder test (DUT), wherein the program instructions are executable to:receive a first one or more measurement configurations from a list ofmeasurement configurations over a first DMA channel; configure the atleast one device according to a first measurement configuration of thefirst one or more measurement configurations; perform at least a portionof one of the plurality of tests according to the first measurementconfiguration; request one or more further measurement configurationsusing the first DMA channel prior to completion of the first one or moremeasurement configurations; receive the one or more further measurementconfigurations over the first DMA channel in response to said requestingthe one or more further measurement configurations, wherein saidreceiving and storing is performed prior to completion of the first oneor more measurement configurations, wherein the one or more furthermeasurement configurations are available for configuring the at leastone device upon completion of the first one or more measurementconfigurations.
 18. A method for configuring at least one deviceaccording to a plurality of measurement configurations for performing aplurality of tests on a device under test (DUT), the method comprising:creating a list of measurement configurations in a computer memory,wherein the list of measurement configurations comprises a plurality ofparameters for configuring operation of the at least one device;creating an intermediate representation of the list of measurementconfigurations; providing a first one or more measurement configurationsfrom the list of measurement configurations to the at least one deviceover a first DMA channel based on the intermediate representation of thelist of measurement configurations; the at least one device storing thefirst one or more measurement configurations; the at least one deviceconfiguring itself according to a first measurement configuration of thefirst one or more measurement configurations; the at least one deviceperforming at least a portion of one of the plurality of tests accordingto the first measurement configuration; the at least one devicerequesting one or more further measurement configurations using thefirst DMA channel prior to completion of the first one or moremeasurement configurations; providing the one or more furthermeasurement configurations from the list of measurement configurationsto the at least one device over the first DMA channel based on theintermediate representation of the list of measurement configurationsand the request; the at least one device storing the one or more furthermeasurement configurations, wherein said storing is performed prior tocompletion of the first one or more measurement configurations, whereinthe one or more further measurement configurations are available forconfiguring the at least one device upon completion of the first one ormore measurement configurations.
 19. A method for configuring at leastone device according to a plurality of measurement configurations forperforming a plurality of tests on a device under test (DUT), the methodcomprising: receiving, by the at least one device, a first measurementconfiguration from a list of measurement configurations over a first DMAchannel; the at least one device storing the first configuration in afirst buffer of the at least one device; the at least one deviceconfiguring itself according to the first measurement configuration; theat least one device performing at least one of the plurality of testsaccording to the first measurement configuration; the at least onedevice requesting a second measurement configuration using the first DMAchannel during at least a portion of either said configuring or saidperforming; receiving, by the at least one device, the secondmeasurement configuration over the first DMA channel in response to saidrequesting the second measurement configuration, wherein said receivingis performed prior to completion of the at least one device performingthe at least one of the plurality of tests according to the firstmeasurement configuration; the at least one device storing the secondmeasurement configuration in a second buffer of the at least one deviceprior to completion of the at least one device performing the at leastone of the plurality of tests according to the first measurementconfiguration; wherein the second configuration is available forconfiguring the at least one device upon completion of the at least oneof the plurality of tests using the first measurement configuration.